G2.7 G2.3 fresh-association qualification residue recovery - #108

Field failure

ARSAS P1.7 bootstrap on physical IED AA1E1F06R4 reached G2.3 and stopped because RequiresFreshAssociation=true: association continuity or cleanup was not proven after a bounded Dynamic DataSet qualification attempt.

The existing coordinator intentionally stops and tells the caller to open a fresh association, but ARSAS had no engine primitive to prove/close the exact temporary NamedVariableList residue before retrying.

Change

Add a narrowly scoped fresh-association recovery primitive for G2.3 qualification residue.

Safety contract:

• run only on an already-fresh MMS association;
• inspect the exact current-run temporary DataSet reference;
• if the temporary list is already absent by NameList + direct directory and the association is healthy, PASS read-only;
• if residue survives, a name match alone is insufficient;
• DeleteNamedVariableList is permitted only when a fresh readable directory exactly matches the failed attempt's ordered member sequence;
• member mismatch/unreadable directory/unhealthy association fails closed with zero delete;
• after targeted delete, re-discover and require namespace absence + direct directory absence + healthy association;
• this API does not bind or enable any RCB and does not change any qualification profile or ProductionEligible state.

Tests pin exact-member, order-sensitive delete authorization and strict fresh closure semantics.